Apparatus and method for interactions with industrial equipment

ABSTRACT

Systems and approaches for interacting with industrial equipment are provided that include an interface having an input and an output, and a processor coupled to the interface. The processor is configured to link a uniform identification construct to a device and receive a request to access the uniform identification construct. The processor is further configured to translate the uniform identification construct into an internet protocol (IP) address and route the request to the device having the uniform identification construct according to the IP address via the output.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a national stage application under 35 U.S.C. §371(c) of prior filed PCT application serial number PCT/US2015/031658,filed May 20, 2015, which claims the benefit under 35 U.S.C. § 119 (e)to U.S. Provisional Application No. 62/013,724 entitled “APPARATUS ANDMETHOD FOR INTERACTIONS WITH INDUSTRIAL EQUIPMENT”, filed Jun. 18, 2014,the content of which is incorporated herein by reference in theirentirety.

BACKGROUND OF THE INVENTION

Field of the Invention

The subject matter disclosed herein generally relates to interactionsbetween users, industrial software, and industrial equipment.

Brief Description of the Related Art

Various systems deploy sensors that are used to obtain different typesof information. These systems also sometimes include actuators thatmanipulate particular devices within these systems to achieve controlobjectives.

One type of system where these sensors and actuators are used involvesindustrial processes. To take one example, an industrial process may usewater pumps and valves. The industrial process may have sensors thatmeasure the temperature and flow of the water exiting the pump. Thepumps may have actuators to turn them on and off.

Because the sensors and actuators are included in industrial processes,they are typically difficult to access. For instance, a user may need togo to the actual industrial plant to read the sensors or to actuate theactuators. This lack of convenience increases the cost of operatingthese sensors/actuators as well as increasing the cost of the entireindustrial process.

The above-mentioned problems have resulted in some user dissatisfactionwith previous approaches.

BRIEF DESCRIPTION OF THE INVENTION

The approaches described herein relate uniform resource locators (URLs),uniform resource identifiers (URIs), or similar constructs and linkthese constructs to certain objects or access points. In one example, anI/O point (e.g., from a programmable logic controller (PLC) or digitalcontrol system (DCS)) is associated with a URL/URI address. In anotherexample, an automation tag from a Supervisory Control and DataAcquisition (SCADA) system or Historian system is associated with aURL/URI address. In another example, an automation object (e.g.,digitally representing a pump, valve, or other automation equipment orobject) is associated with a URL/URI.

This present approaches provide for interacting with industrialequipment or information in the context of the modern Internet. Themethodology uses Internet addresses (e.g., URLs, URIs, IPv4 addresses,and IPv6 addresses to mention a few examples) to expose a flat orstructured namespace for industrial information. For example, anyvariable or structured data associated with sensors, personal computers,programmable logic controllers, distributed control systems, specialtycontrollers, supervisory control and data acquisition (SCADA) systems,Historians, and other automation processes are exposed to access by auser via a URL, URI, IPv4 address or IPv6 address (to mention a fewexamples of address constructs).

In many of these embodiments, a uniform resource locator (e.g., URL) islinked to a device (e.g., a sensor in an industrial process). A requestto access the URL is made from a client based application such as a webbrowser. The URL is translated into an IP address, which allows therequest to be routed to the device associated with the URL. The deviceprocesses the request with a response, which can include informationsought by the requestor. In other examples, the IP address is associatedwith a set point, and this set point is changeable by utilizing the IPaddress to post the change.

In some approaches, an apparatus having an interface and a processor isprovided. The processor is configured to link a construct with anindustrial data object and receive a request via the input from anapplication to access the industrial data object by using the construct.The application may include at least one of a client-based applicationor a web-based server. The processor is then configured to respond tothe request by routing the industrial data object to the application viathe output. It is understood that any number of processors, locatedremotely or locally relative to each other, may be used in theseapproaches.

In many of these approaches, the construct comprises at least one of anInternationalized Resource Identifier (IRI), a uniform resourceidentifier (URI), a uniform resource locator (URL), an IPv4 address, anIPv6 address, an IPv6 address associated with an IEEE 64 bit extendedaddress, or a 16 bit address unique to a local Personal Area Network(PAN). The industrial data object may include at least one of a device,an attribute or a number of attributes within a device, or a propertywithin an object. The device may include any number of sensors,actuators such as pumps or valves, or controllers.

In some approaches, the processor is further configured to request andreceive permission to access the device. The processor may furthertranslate the construct into an internet protocol (IP) address which maybe associated with any number of set points and/or measurands. In someforms, this set point is changeable.

In yet other approaches, a construct is linked with an industrial dataobject. A request is then received from an application to access theindustrial data object by using the construct. The request is thenresponded to by routing the industrial data object to the application.

In some of these forms, the step of linking the construct includeslinking at least one of a uniform identification construct or a semanticconstruct (subject-predicate-object-triplet). Further, these approachesmay initiate a request by the application using the construct to accessthe industrial data object. The construct may also be translated into anIP address.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the disclosure, reference should bemade to the following detailed description and accompanying drawingswherein:

FIG. 1 comprises a block diagram of a system where URLs (or othersimilar constructs) are linked to various aspects of industrialprocesses according to various embodiments of the present invention;

FIG. 2 comprises a block diagram of a system where URLs (or othersimilar constructs) are linked to various aspects of industrialprocesses according to various embodiments of the present invention;

FIG. 3 comprises a block diagram of a system where URLs (or othersimilar constructs) are linked to various aspects of industrialprocesses according to various embodiments of the present invention;

FIG. 4 comprises a block diagram of an approach for providing securityin a system where URLs (or other similar constructs) are linked tovarious aspects of industrial processes according to various embodimentsof the present invention.

Skilled artisans will appreciate that elements in the figures areillustrated for simplicity and clarity. It will further be appreciatedthat certain actions and/or steps may be described or depicted in aparticular order of occurrence while those skilled in the art willunderstand that such specificity with respect to sequence is notactually required. It will also be understood that the terms andexpressions used herein have the ordinary meaning as is accorded to suchterms and expressions with respect to their corresponding respectiveareas of inquiry and study except where specific meanings have otherwisebeen set forth herein.

DETAILED DESCRIPTION OF THE INVENTION

The approaches described herein allow sensors and other equipment to beuniquely identified by an URI or similar constructs (e.g., URL, IPv4address, or IPv6 address to mention a few examples). These approachesallow any system component including individual sensors to be accessiblewithin the context of the modern Internet using, for example, a URL,URI, IPv4 address, or IPv6 address. This enables machine-to-machine,machine-to-device, sensor-to-machine and sensor-to-sensor communicationsto be built on and leveraging existing communication channels andtechnology, thus eliminating the need for a separate infrastructure,such as a traditional SCADA system, to enable industrial Internetapplications.

In one aspect, the present approaches provide interconnectivity betweendevices, machines and sensors in a scalable and secure fashion. Thisallows easier user interaction since a user does not have to remembercomplicated addresses or protocols. The present approaches are alsoeasier to use since a user can access the appropriate URL from anyterminal or interface that is connected to Internet.

In one example, I/O points can be associated with and available to auser as an URL/URI address. This reference and linkage allows for accessto each I/O point individually. The URL can contain paths to resourceshosted by the I/O point or fragments identifying the relevant section inthe document object model (DOM) to allow users to access metadata aboutthe instrument and its measured value. This provides knowledge to theuser about current state. These approaches can be extended to themanipulation of set points and/or outputs.

In some aspects, each input point may use digital signatures toauthenticate that requests for information originated from a known user.Each output also may require a digital signature to authenticate that arequest to change or manipulate the output came from a known user withthe required authorization to make changes to outputs.

In another example, an automation tag from a SCADA or Historian systemcan be associated with and available to a user as a URL/URI address.This association eliminates the translation step required from having atag name and translating it to its network address. Simplifying thesystem in this way removes a level of abstraction. Users can use asimple web browser to display tag values or other information pertinentto a SCADA tag. Users could access information such as engineeringunits, diagnostics and alarms to mention a few examples. Any device(mobile or computer) that supports web based access could view thisinformation.

As with I/O point associations, security may be provided. Additionally,this approach could be used to control the information. For example,users could move set points, manipulate the data, and so forth.

In another example, an automation object (digitally representing a pump,valve, or other automation equipment or object) may be associated withand available to users as a URL/URI.

In a Manufacturing Execution System (MES), this approach could extend tovarious forms and processes being made available. For example, a ShopOrder may be available as an URL/URI.

Human Machine Interface (HMI) and SCADA system information could formprocess objects that represent equipment (i.e. pumps) and aggregate thatinformation into a set of data that can be made available through aURL/URI. To take one example, different things, parts, or attributesthat comprise a pump could be accessible such as motor temperatures,flow rate, speed, to mention a few examples.

As with I/O point and SCADA associations, security may be provided.Additionally, this approach could be used to control the information viathe URL. For example, users could move set points, manipulate the data,and so forth.

It will be appreciated that in many of the examples described herein,URLs are associated with various entities. However, it will beunderstood that the approaches described herein are not limited toassociations with URLs, but also include associations with URIs, IPv4addresses, IPv6 addresses, or any construct that is easily remembered bya human user.

Referring now to FIG. 1, one example of an arrangement that linksuniform resource locators (URLs) to industrial equipment is described.The system 100 includes a mobile unit 102, the Internet (or an intranet)104, a display 106, a web server 108, an industrial controller 110, anda distributed I/O device 103. The web server 108, first industrialcontroller 110, and distributed I/O device 103 are coupled together viaa communication network 112. The web server as represented in thedrawings is shown as a distinct entity, but it may be an integratedcomponent in the other hardware (any component including the web serverand sensors to mention two examples).

The mobile unit 102 is in this example a portable unit that is coupledto the Internet 104 via either a wired or wireless connection. Forexample, the mobile unit 102 may be a cellular phone, lap top computer,tablet, or similar device.

The Internet 104 is the publically available Internet and includesservers, switches, routers, gateways, sub-networks, domain name servicesand so forth. The Internet 104 can instead be an intranet and localizedto a particular company, school, building, or organization to mention afew examples.

The display 106 is a fixed screen and may be connected to a personalcomputer in one example. The web server 108 listens for requests comingover the Internet 104 that originate from clients 102 and 106. The webserver 108 is shown as an individual entity, but it can be part of theIndustrial Controller (110, 120, 122, 124), Distributed I/O (103, 130,132) and/or Sensors (126, 136). Once the web server receives a requestit responds by routing the requested resource, e.g. the measurementreading, given by the URI back to the client over the Internet 104. Itis understood that in some approaches, the web server 108 may be anapparatus having an interface with at least one input and an output anda processor coupled thereto. Accordingly, the processor of the webserver 108 may be configured to link a construct with an industrial dataobject by using the construct, receive a request via the input from anapplication (e.g. clients 102 and/or 106) to access the industrial dataobject by using the construct, and respond to the request by routing theindustrial data object to the application via the output of the webserver 108.

The industrial controller 110 includes a CPU 120, a first I/O card 122,and a second I/O card 124. The first I/O card 122 couples to a firsttemperature sensor 126. The distributed I/O device 103 includes anetwork interface 130, a third I/O card 132, and a fourth I/O card 134.The third I/O card 132 couples to a second temperature sensor 136.

The first temperature sensor 126 has a URL of Plant1.Unit1.temp, whichtranslates to a resource accessible with the Internet address of3.1.2.5. The second temperature sensor 136 has a URL ofPlant1.Unit2.temp, which translates in one example to a resourceaccessible with the Internet address of 3.1.2.5. In this example, thesecond temperature sensor 136 has a reading of 67 degrees F.

The CPU 120 can act either as a gateway, a server, a router, or a switchto provide direct network access to devices on its backplane or throughits remote interface connections such as Profibus or other fieldnetworks. The temperature sensors 126 or 136 could also be directlyconnected to the communication network 112, but in either case accesslooks exactly the same to other devices on the network.

It will be understood that the web server 108 translates the URL into anIP address. In one aspect, the actual sequence is that the URL isentered in the browser and an HTTP request is made from the browser. TheInternet 104 has domain name services that resolve the URL in therequest to an IP address, which is the address of the web server 108. Inthese approaches and in one example, the temperatures and otherinformation are resources that the web server 108 can serve up toclients. The web server 108 listens for requests from clients andresponds to those requests. URLs are a subset of URIs. The URI cancontain location paths for specific resources that are accessible fromthe web server 108, such as current values or other metadata.

URLs are a subset of URIs. The URI can contain location paths forspecific resources that are accessible from the web server 108, such ascurrent values or other metadata.

In operation, a user at the mobile unit 102 or display 106 desires thatthe temperature of temperature sensor 136 be displayed. They enter theuser/human-friendly URI Plant1.Unit2.temp. This initiates a request overthe Internet 104 for the resource identified by the URI. The request isprocessed by the web server 108 and a response with the temperaturereading is sent back to the mobile unit 102 or display 106. The devices102 and 106 render the temperature reading.

Referring now to FIG. 2, another example of an arrangement that linksuniform resource locators (URLs) to industrial equipment is described.The system 200 includes a mobile unit 202, the Internet (or intranet)204, a display 206, a web-enabled Supervisory Control and DataAcquisition (SCADA) node or server 208, a web server 210, and a SCADAtemperature sensor 212 (represented by a SCADA tag Temp1).

The mobile unit 202 is in this example a portable unit that is coupledto the Internet 204 via either a wired or wireless connection. Forexample, the mobile unit 202 may be a cellular phone, lap top computer,tablet, or similar device.

The Internet 204 is the publically available Internet and includesservers, switches, routers, gateways, sub-networks, domain name servicesand so forth. The Internet 204 can instead be an intranet and localizedto a particular company, school, building, or organization to mention afew examples.

The display 206 is a fixed screen and may be connected to a personalcomputer in one example. The domain name services converts URLs into IPaddresses in order to route messages across the Internet 204 to theappropriate server.

The temperature sensor 212 has a URL of SCADANode1.Temp1 (whichtranslates in one example to an Internet address of 3.26.4.1). Inoperation, a user at the mobile unit 202 or display 206 desires that thetemperature of temperature sensor 212 be displayed. The user enters theuser/human-friendly URI of SCADANode1.Temp1. This initiates a requestover the Internet 204 for the resource identified by the URI.

SCADA server 208 is configured and programmed to receive requests overthe internet for resources (e.g. the value of a SCADA tag) that ithosts. The server responds to the request with information indicatingthe temperature measured by the temperature sensor 212. This informationis sent back via the web server 210, across the Internet 204, to thedisplay 206 or mobile unit 202. Once reaching the display 206 or mobileunit 202, the information is rendered to the user.

Referring now to FIG. 3, still another example of an arrangement thatlinks uniform resource locators (URLs) to industrial equipment isdescribed. The system 300 includes a mobile unit 302, the Internet (orintranet) 304, a display 306, a web-enabled equipment object 308, and aweb server 310. The equipment object (in this example, a pump), is acomplex piece of equipment that has several attributes 320-332. Theattributes are discussed in greater detail below.

The mobile unit 302 is in this example is a portable unit that iscoupled to the Internet 304 via either a wired or wireless connection.For example, the mobile unit 302 may be a cellular phone, lap topcomputer, tablet, or similar device.

The Internet 304 is the publically available Internet and includesservers, switches, routers, gateways, sub-networks, and so forth. TheInternet 304 can instead be an intranet and localized to a particularcompany, school, building, or organization to mention a few examples.

The display 306 is a fixed screen and may be connected to a personalcomputer in one example. The web server 310 listens for requests fromclients via the internet.

The equipment object 308 is a complex piece of equipment that has a webinterface configured and programmed to receive requests over theinternet for resources that it hosts. The equipment object 308 mayitself have a URL, in this case Pump.p100 that translates in one exampleinto IP address of 3.26.4.1. As mentioned, the equipment object has itsown attributes including a HMI faceplate reference 320, a simulationmodel reference 322, analytics data 324, alarm data 326, HMI Mimicreference 328, Historical data 330, and controls logic reference 332. Itwill be appreciated that each of these attributes may have its ownunique URI given by a specific location path. It will also be understoodthat other attributes are possible.

The HMI faceplate reference 320 is a small graphical interface. In oneexample, it is a graphical representation of the control interface(e.g., showing knobs).

The simulation model reference 322 is a digital representation of amodel. A user can use the model to test hypothetical inputs to see theoutput without using the real device (e.g., the real pump).

The analytics data 324 represents key performance indicators. Forexample, temperature and pressure may represent key performanceindicators. The analytics data 324 may indicate the value of theseindicators as well.

The alarm data 326 represents run-time data representing potentiallyadverse conditions. For example, a low flow condition may be indicatedby this data.

The HMI Mimic reference 328 is a graphical representation of an objectthat may also be used to indicate condition. In one example, this may bea pump icon that changes colors based upon the condition of the pump.

The Historical data 330 represents historical run-time data of thesystem. For example, values of sensors over time may be shown.

The controls logic reference 332 is control logic for the industrialequipment. For example, this may represent a particular algorithmregarding pump operation.

In operation, a user at the mobile unit 302 or display 306 desires thatan attribute be displayed. They enter the user/human-friendly URI ofPump.p100.mimic for the mimic object associated with the pump. —Thisinitiates a request for the mimic object resource that is routed to theweb interface 310. Upon receipt of the request, the web interface 310responds by sending the mimic object resource, back across the Internet304, to the display 306 or mobile unit 302. Once reaching the display306 or mobile unit 302, the information is rendered to the user.

It will be appreciated that the present approaches can be used todisplay existing information or readings of sensors or other measurementdevices. Additionally, the approaches can be used to actuate devices,processes, or otherwise alter the operation of a physical entity. Forexample, a user at any of the mobile devices may enter a URL to change aset point (a desired condition) of a process or device. For example, acertain URL can be used to change the set point temperature of amachine. Another URL can be used to influence the position of a valve.

Referring now to FIG. 4, one example of addressing security issues usingthe present approaches is described. These approaches can be used at oneof the mobile unit or terminal so that a user at one of these devicescan access or alter a process by using the URL-based approachesdescribed herein. In one aspect, the user asks for and receivespermission to access the industrial process before they are allowed toproceed.

At step 402, the user sends a digital signature from their device to theunit that is the destination unit (e.g., the input point, the SCADAserver, or the equipment object). At step 404, the destination unitverifies the signature is valid. At step 406, the destination unit sendsapproval to the user. At step 408, the user sends encrypted data to thedestination unit.

It will be appreciated by those skilled in the art that modifications tothe foregoing embodiments may be made in various aspects. Othervariations clearly would also work, and are within the scope and spiritof the invention. It is deemed that the spirit and scope of thatinvention encompasses such modifications and alterations to theembodiments herein as would be apparent to one of ordinary skill in theart and familiar with the teachings of the present application.

What is claimed is:
 1. A method comprising: linking, by a processor, aconstruct with an industrial data object that represents an industrialequipment including a sensor, wherein the industrial data object hosts aplurality of attributes for the industrial equipment, and wherein theconstruct comprises a semantic construct in the form of at least one ofan Internationalized Resource Identifier (IRI), a uniform resourceidentifier (URI), or a uniform resource locator (URL) that specifies aparticular attribute among the plurality of attributes hosted by theindustrial data object in the semantic construct, wherein the particularattribute corresponds to a sensor measurement reading output from theindustrial equipment; receiving, by the processor, a request includingthe construct from an application to access the sensor measurementreading via the particular attribute; translating, by the processor, theconstruct into an internet protocol (IP) address that is associated withthe sensor measurement reading output from the industrial equipment; andresponding, at the direction of the processor to the request, by routingthe sensor measurement reading to the application for displaying thesensor measurement reading.
 2. The method of claim 1, wherein theindustrial equipment further comprises at least one of an actuator or acontroller.
 3. The method of claim 1, further comprising: receiving arequest to alter operation of the industrial equipment or change theparticular attribute of the industrial equipment; and responding to therequest by routing the industrial data object to the application, thusaffecting the operation of the industrial equipment or changing theparticular attribute of the industrial equipment.
 4. An apparatuscomprising: an interface having at least one input and an output; and aprocessor coupled to the interface, wherein the processor is configuredto: link a construct with an industrial data object that represents anindustrial equipment including a sensor, wherein the industrial dataobject hosts a plurality of attributes for the industrial equipment, andwherein the construct comprises a semantic construct in the form of atleast one of an Internationalized Resource Identifier (IRI), a uniformresource identifier (URI), or a uniform resource locator (URL) thatspecifies a particular attribute among the plurality of attributeshosted by the industrial data object in the semantic construct, whereinthe particular attribute corresponds to a sensor measurement readingoutput from the industrial equipment; receive a request including theconstruct via the input from an application to access the sensormeasurement reading via the particular attribute; translate theconstruct into an internet protocol (IP) address that is associated withthe sensor measurement reading output from the industrial equipment; andrespond to the request by routing the sensor measurement reading to theapplication via the output for displaying the sensor measurementreading.
 5. The apparatus of claim 4, wherein the industrial equipmentfurther comprises at least one of an actuator or a controller.
 6. Theapparatus of claim 4, wherein the processor is further configured to:receive a request to alter operation of the industrial equipment orchange the particular attribute of the industrial equipment; and respondto the request by routing the industrial data object to the application,thus affecting the operation of the industrial equipment or changing theparticular attribute of the industrial equipment.